Skip to main content

Chrome Installation

Requirements​

  • Supported on Windows, macOS, and Linux.
  • Chrome Stable channel only
  • Sensor version 25.04 and later (self-hosted)
    • Extension ID: hbicflpnhfmdndpibdegbnkkpngjbhfh
    • Update URL: https://<your-domain>.cyberhaven.io/v1/extensions/chromium/update
  • Sensor versions before 25.04
    • Manifest V2: dcnmjapddamaigjddfkifoklhnomddkd
    • Manifest V3: pajkjnmeojmbapicmbpliphjmcekeaac

Chrome Installation​

Cyberhaven’s Chrome browser extension can be deployed and managed as a self‑hosted extension or via the Chrome Web Store, depending on your Sensor version, below are the instructions for various methods of installation.

For IDs, update URLs, ports, and other prerequisites, see: Browser Extensions Prerequisites.

If issues are encountered please check the Browser Extensions Troubleshooting for information on how to troubleshoot.

Windows: Sensor-managed auto‑install (default)​

  • The Windows Endpoint Sensor automatically installs and updates the Chrome extension.
  • If you prefer to manage the extension via GPO/Intune, contact Customer Support to disable Sensor-managed updates for Chrome.

Windows: Chrome Installation via Group Policy​

  1. Install Google Chrome ADMX templates and open Group Policy Management Editor.
  2. Go to Computer Configuration > Administrative Templates > Google > Google Chrome > Extensions.
  3. Enable Configure the list of force-installed apps and extensions.
  4. Add the Cyberhaven Chrome extension using the ID and update URL from the prerequisites page, in the format:
    • <extension_id>;<update_url>
    • Example (self-hosted, Sensor 25.04+): <id-from-prereqs>;<tenant-chromium-update-url-from-prereqs>
  5. Apply policy, then verify under chrome://policy and chrome://extensions.

Tip: If policies don’t apply immediately, run gpupdate /force and restart Chrome.

Installation via Microsoft Intune​

  • Use Settings Catalog for Google Chrome > Extensions to force-install the extension.
  • Provide the extension ID and update URL from the prerequisites page.
  • Target the assignment to the appropriate device/user groups.

Installation via Chrome Browser Cloud Management​

Use Google Admin to deploy the extension to managed Chrome browsers across Windows, macOS, and Linux.

  1. Sign in to Google Admin with a super admin and open: https://admin.google.com/ac/chrome/apps/user
  2. Select the organizational unit (OU) to target (or keep the top‑level domain to deploy to all users).
  3. Open the Users & browsers tab and click the + button (bottom right).
  4. Choose Add Chrome app or extension by ID.
  5. Enter the extension ID based on your Sensor version and deployment method:
    • Self‑hosted (Sensor 25.04+): use the self‑hosted extension ID from prerequisites
    • Chrome Web Store: use the store extension ID from prerequisites
  6. Update URL:
    • Self‑hosted (Sensor 25.04+): from the drop‑down, select “From a custom URL”, then enter your tenant Chromium update URL (see prerequisites), and Save.
    • Chrome Web Store (earlier sensors): use the store default (no custom URL). If your console requires an explicit URL, use https://clients2.google.com/service/update2/crx.
  7. Confirm the Cyberhaven security extension appears in the Apps table for the OU.
  8. Set Installation policy to Force install.
  9. Set Permissions and URL access to Allow all permissions.
  10. Under Deployment settings, set Update URL to Installation URL so Chrome checks the installation URL for updates.
  11. Click Save. The extension deploys on the next managed‑browser policy check‑in.

Cleanup for macOS MDM​

  • After confirming Google Admin deployment, you may remove the com.google.Chrome Application payload from the Cyberhaven mobileconfig to avoid policy conflicts. If using Jamf, delete the Chrome policy section matching your deployment method (self‑hosted vs. store) from the imported profile.

macOS: Installation via Cyberhaven MDM Profile​

  • Deploy Cyberhaven.mobileconfig (version noted in prerequisites) to managed Macs. The profile force-installs the extension.
  • Chrome may take a few minutes to refresh policies; you can force refresh at chrome://policy.
  • The installed extension ID depends on Sensor version. Refer to the prerequisites page for the correct ID and update URL.

macOS: Installation via Jamf and Other MDMs​

If you manage Chrome policies directly in your MDM (instead of using the Cyberhaven profile), configure the extension policy equivalent to:

com.google.Chrome
  ExtensionSettings
    <extension_id-from-prereqs>
      installation_mode = force_installed
      update_url        = <update-url-from-prereqs>
      override_update_url = true

Remove duplicate Chrome policy blocks from Cyberhaven.mobileconfig to avoid conflicts if you manage the extension elsewhere.

Installation Verification​

  • On endpoints, check chrome://policy (Reload Policies) and chrome://extensions for the Cyberhaven extension.
  • In the Console, verify endpoints reflect the extension state after policy sync.